-
Notifications
You must be signed in to change notification settings - Fork 706
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not execute "regress" CI on PR #1535
Conversation
To reduce the CI execution time on servers
@cathales Can you approve ? |
✔️ successful run, report available here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I’m looking forward to two changes so that switching PR CI from regress to dev actually reduces latency for contributors:
- an FPGA build optimization (eg: caching Vivado primitives)
- triggering the Thales CI from a GitHub webhook on PR&master pushes instead of on schedule
Agree on the two improvement proposals |
Update: this should be working from now 🚀 @JeanRochCoulon should we create a task to investigate possible FPGA build duration optimizations? |
Yes and you can assign our specialist: Guillaume |
It seems I’m not allowed to add tasks |
Give me the texte you would like to add in kanban board, I will do the job |
To reduce the CI execution time on servers